File and print server cluster problems

Cause:  WINS or DNS might not be correctly configured.

Solution:  Make sure that WINS or DNS are correctly configured.

If you are using WINS, run WINS Manager on the WINS server; then, on the Mappings menu, click Show Database. Make sure that each node and the cluster are registered in the WINS database and that the registrations are active.

For more information on WINS and WINS Manager, see the Networking Guide in the Microsoft Windows Server 2003 Resource Kit.

Cause:  Your security policies might not allow the client to access the file share.

Solution:  Make sure that your security policies allow the client to access the file share.

The client must have the right to log on to the file share, or the Guest account must be enabled for the client to have access.

Cause:  Not all printer ports may be used in a server cluster.

Solution:  Use cluster-aware ports, for example LPR or Standard TCP/IP ports.

The LPR and Standard TCP/IP Port, both provided with Windows Server 2003 family operating systems, can be used in a server cluster. Check your printer documentation to verify that your printer can use one of these two ports.

For more information, see To create a cluster-managed printer.

Cause:  The share name for the printer may also used by another printer in the cluster.

Solution:  Choose a unique share name for the printer.

We recommend that you do not use the same share name for different printers, even if they are in a different resource group and associated with a different Print Spooler resource. In the event of a failure, the same node in the cluster may own both resource groups. If this occurs, printers that share a common name will not be available.